Apparatus of GNB to enable an inactive mode in dual connectivity

ABSTRACT

Embodiments of a next generation Node-B (gNB), User Equipment (UE) and methods for communication are generally described herein. A gNB may be configurable to operate as a master gNB (MgNB). The MgNB may transmit radio-resource control (RRC) signaling to provide information for dual connectivity to allow the UE to utilize radio resources of both a master cell group (MCG) associated with the MgNB and a secondary cell group (SCG) associated with a secondary gNB (SgNB). The MgNB may transmit, to the SgNB, an SgNB release request message that indicates a partial suspension of the dual connectivity, wherein: a first portion of a configuration for the SCG is to be maintained and a second portion of the configuration for the SCG is to be released.

PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No.16/475,056, filed Jun. 28, 2019, which is a U.S. National Stage Filingunder 35 U.S.C. 371 from International Application No.PCT/US2018/037551, filed Jun. 14, 2018 and published in English as WO2018/232124 on Dec. 20, 2018, which claims priority to U.S. ProvisionalPatent Application Ser. No. 62/521,186, filed Jun. 16, 2017, each ofwhich is incorporated herein by reference in its entirety.

The claims in the instant application are different than those of theparent application and/or other related applications. The Applicanttherefore rescinds any disclaimer of claim scope made in the parentapplication and/or any predecessor application in relation to theinstant application. Any such previous disclaimer and the citedreferences that it was made to avoid, may need to be revisited. Further,any disclaimer made in the instant application should not be read intoor against the parent application and/or other related applications.

TECHNICAL FIELD

Embodiments pertain to wireless communications. Some embodiments relateto wireless networks including 3GPP (Third Generation PartnershipProject) networks, 3GPP LTE (Long Term Evolution) networks, and 3GPPLTE-A (LTE Advanced) networks. Some embodiments relate to FifthGeneration (5G) networks. Some embodiments relate to New Radio (NR)networks. Some embodiments relate to usage of an inactive mode. Someembodiments relate to suspension and/or resumption of bearers. Someembodiments relate to dual connectivity (DC) arrangements.

BACKGROUND

Base stations and mobile devices operating in a cellular network mayexchange data. Various techniques may be used to improve capacity,battery life and/or performance, in some cases. In an example, a mobiledevice may communicate with two base stations in a dual connectivity(DC) arrangement. In this scenario, a performance benefit may berealized. However, some operations may become challenging, such asexchanging of control signaling between the mobile device and the basestations and/or exchanging of control signaling between the basestations. Accordingly, there is a general need for methods and systemsto perform operations related to dual connectivity in these and otherscenarios.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a functional diagram of an example network in accordance withsome embodiments;

FIG. 1B is a functional diagram of another example network in accordancewith some embodiments.

FIG. 2 illustrates a block diagram of an example machine in accordancewith some embodiments,

FIG. 3 illustrates a user device in accordance with some aspects;

FIG. 4 illustrates a base station in accordance with some aspects;

FIG. 5 illustrates an exemplary communication circuitry according tosome aspects:

FIG. 6 illustrates the operation of a method of communication inaccordance with some embodiments:

FIG. 7 illustrates the operation of another method of communication inaccordance with some embodiments;

FIG. 8 illustrates the operation of another method of communication inaccordance with some embodiments;

FIG. 9 illustrates example operations in accordance with someembodiments:

FIG. 10 illustrates additional example operations in accordance withsome embodiments; and

FIG. 11 illustrates additional example operations in accordance withsome embodiments.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1A is a functional diagram of an example network in accordance withsome embodiments. FIG. 1B is a functional diagram of another examplenetwork in accordance with some embodiments. In some embodiments, thenetwork 100 may be a Third Generation Partnership Project (3GPP)network. In some embodiments, the network 150 may be a 3GPP network. Ina non-limiting example, the network 150 may be a new radio (NR) network.It should be noted that embodiments are not limited to usage of 3GPPnetworks, however, as other networks may be used in some embodiments. Asan example, a Fifth Generation (5G) network may be used in some cases.As another example, a New Radio (NR) network may be used in some cases.As another example, a wireless local area network (WLAN) may be used insome cases. Embodiments are not limited to these example networks,however, as other networks may be used in some embodiments. In someembodiments, a network may include one or more components shown in FIG.1A. Some embodiments may not necessarily include all components shown inFIG. 1A, and some embodiments may include additional components notshown in FIG. 1A. In some embodiments, a network may include one or morecomponents shown in FIG. 1B. Some embodiments may not necessarilyinclude all components shown in FIG. 1B, and some embodiments mayinclude additional components not shown in FIG. 1B. In some embodiments,a network may include one or more components shown in FIG. 1A and one ormore components shown in FIG. 1B. In some embodiments, a network mayinclude one or more components shown in FIG. 1A, one or more componentsshown in FIG. 1B and one or more additional components.

The network 100 may comprise a radio access network (RAN) 101 and thecore network 120 (e.g., shown as an evolved packet core (EPC)) coupledtogether through an S1 interface 115. For convenience and brevity sake,only a portion of the core network 120, as well as the RAN 101, isshown. In a non-limiting example, the RAN 101 may be an evolveduniversal terrestrial radio access network (E-UTRAN). In anothernon-limiting example, the RAN 101 may include one or more components ofa New Radio (NR) network. In another non-limiting example, the RAN 101may include one or more components of an E-UTRAN and one or morecomponents of another network (including but not limited to an NRnetwork).

In some embodiments, an NG-RAN may support Multi-RAT Dual Connectivity(MR-DC) operation whereby a UE 102 in RRC_CONNECTED is configured toutilize radio resources provided by two distinct schedulers, located intwo different NG-RAN nodes connected via a non-ideal backhaul andproviding either E-UTRA (i.e. if the node is an ng-eNB 104) or NR access(i.e. if the node is a gNB 105).

The core network 120 may include a mobility management entity (MME) 122,a serving gateway (serving GW) 124, and packet data network gateway (PDNGW) 126. In some embodiments, the network 100 may include (and/orsupport) one or more Evolved Node-B's (eNBs) 104 (which may operate asbase stations) for communicating with User Equipment (UE) 102. The eNBs104 may include macro eNBs and low power (LP) eNBs, in some embodiments.

In some embodiments, the network 100 may include (and/or support) one ormore Next Generation Node-B's (gNBs) 105. In some embodiments, one ormore eNBs 104 may be configured to operate as gNBs 105. Embodiments arenot limited to the number of eNBs 104 shown in FIG. 1A or to the numberof gNBs 105 shown in FIG. 1A. In some embodiments, the network 100 maynot necessarily include eNBs 104. Embodiments are also not limited tothe connectivity of components shown in FIG. 1A.

It should be noted that references herein to an eNB 104 or to a gNB 105are not limiting. In some embodiments, one or more operations, methodsand/or techniques (such as those described herein) may be practiced by abase station component (and/or other component), including but notlimited to a gNB 105, an eNB 104, a serving cell, a transmit receivepoint (TRP) and/or other. In some embodiments, the base stationcomponent may be configured to operate in accordance with a New Radio(NR) protocol and/or NR standard, although the scope of embodiments isnot limited in this respect. In some embodiments, the base stationcomponent may be configured to operate in accordance with a FifthGeneration (5G) protocol and/or 5G standard, although the scope ofembodiments is not limited in this respect.

In some embodiments, one or more of the UEs 102 and/or eNBs 104 may beconfigured to operate in accordance with an NR protocol and/or NRtechniques. References to a UE 102, eNB 104 and/or gNB 105 as part ofdescriptions herein are not limiting. For instance, descriptions of oneor more operations, techniques and/or methods practiced by a gNB 105 arenot limiting. In some embodiments, one or more of those operations,techniques and/or methods may be practiced by an eNB 104 and/or otherbase station component.

In some embodiments, the UE 102 may transmit signals (data, controland/or other) to the gNB 105, and may receive signals (data, controland/or other) from the gNB 105. In some embodiments, the UE 102 maytransmit signals (data, control and/or other) to the eNB 104, and mayreceive signals (data, control and/or other) from the eNB 104. Theseembodiments will be described in more detail below.

The MME 122 is similar in function to the control plane of legacyServing GPRS Support Nodes (SGSN). The MME 122 manages mobility aspectsin access such as gateway selection and tracking area list management.The serving GW 124 terminates the interface toward the RAN 101, androutes data packets between the RAN 101 and the core network 120. Inaddition, it may be a local mobility anchor point for inter-eNBhandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement. The serving GW 124 and the MME 122 may be implemented inone physical node or separate physical nodes. The PDN GW 126 terminatesan SGi interface toward the packet data network (PDN). The PDN GW 126routes data packets between the EPC 120 and the external PDN, and may bea key node for policy enforcement and charging data collection. It mayalso provide an anchor point for mobility with non-LTE accesses. Theexternal PDN can be any kind of IP network, as well as an IP MultimediaSubsystem (IMS) domain. The PDN GW 126 and the serving GW 124 may beimplemented in one physical node or separated physical nodes.

In some embodiments, the eNBs 104 (macro and micro) terminate the airinterface protocol and may be the first point of contact for a UE 102.In some embodiments, an eNB 104 may fulfill various logical functionsfor the network 100, including but not limited to RNC (radio networkcontroller functions) such as radio bearer management, uplink anddownlink dynamic radio resource management and data packet scheduling,and mobility management.

In some embodiments, UEs 102 may be configured to communicate OrthogonalFrequency Division Multiplexing (OFDM) communication signals with an eNB104 and/or gNB 105 over a multicarrier communication channel inaccordance with an Orthogonal Frequency Division Multiple Access (OFDMA)communication technique. In some embodiments, eNBs 104 and/or gNBs 105may be configured to communicate OFDM communication signals with a UE102 over a multicarrier communication channel in accordance with anOFDMA communication technique. The OFDM signals may comprise a pluralityof orthogonal subcarriers.

The S1 interface 115 is the interface that separates the RAN 101 and theEPC 120. It may be split into two parts: the S1-U, which carries trafficdata between the eNBs 104 and the serving GW 124, and the S1-MME, whichis a signaling interface between the eNBs 104 and the MME 122. The X2interface is the interface between eNBs 104. The X2 interface comprisestwo parts, the X2-C and X2-U. The X2-C is the control plane interfacebetween the eNBs 104, while the X2-U is the user plane interface betweenthe eNBs 104.

In some embodiments, similar functionality and/or connectivity describedfor the eNB 104 may be used for the gNB 105, although the scope ofembodiments is not limited in this respect. In a non-limiting example,the S1 interface 115 (and/or similar interface) may be split into twoparts: the S1-U, which carries traffic data between the gNBs 105 and theserving GW 124, and the S1-MME, which is a signaling interface betweenthe gNBs 104 and the MME 122. The X2 interface (and/or similarinterface) may enable communication between eNBs 104, communicationbetween gNBs 105 and/or communication between an eNB 104 and a gNB 105.

With cellular networks, LP cells are typically used to extend coverageto indoor areas where outdoor signals do not reach well, or to addnetwork capacity in areas with very dense phone usage, such as trainstations. As used herein, the term low power (LP) eNB refers to anysuitable relatively low power eNB for implementing a narrower cell(narrower than a macro cell) such as a femtocell, a picocell, or a microcell. Femtocell eNBs are typically provided by a mobile network operatorto its residential or enterprise customers. A femtocell is typically thesize of a residential gateway or smaller and generally connects to theuser's broadband line. Once plugged in, the femtocell connects to themobile operator's mobile network and provides extra coverage in a rangeof typically 30 to 50 meters for residential femtocells. Thus, a LP eNBmight be a femtocell eNB since it is coupled through the PDN GW 126.Similarly, a picocell is a wireless communication system typicallycovering a small area, such as in-building (offices, shopping malls,train stations, etc.), or more recently in-aircraft. A picocell eNB cangenerally connect through the X2 link to another eNB such as a macro eNBthrough its base station controller (BSC) functionality. Thus, LP eNBmay be implemented with a picocell eNB since it is coupled to a macroeNB via an X2 interface. Picocell eNBs or other LP eNBs may incorporatesome or all functionality of a macro eNB. In some cases, this may bereferred to as an access point base station or enterprise femtocell. Insome embodiments, various types of gNBs 105 may be used, including butnot limited to one or more of the eNB types described above.

In some embodiments, the network 150 may include one or more componentsconfigured to operate in accordance with one or more 3GPP standards,including but not limited to an NR standard. The network 150 shown inFIG. 1B may include a next generation RAN (NG-RAN) 155, which mayinclude one or more gNBs 105. In some embodiments, the network 150 mayinclude the E-UTRAN 160, which may include one or more eNBs. The E-UTRAN160 may be similar to the RAN 101 described herein, although the scopeof embodiments is not limited in this respect.

In some embodiments, the network 150 may include the MME 165. The MME165 may be similar to the MME 122 described herein, although the scopeof embodiments is not limited in this respect. The MME 165 may performone or more operations or functionality similar to those describedherein regarding the MME 122, although the scope of embodiments is notlimited in this respect.

In some embodiments, the network 150 may include the SGW 170. The SGW170 may be similar to the SGW 124 described herein, although the scopeof embodiments is not limited in this respect. The SGW 170 may performone or more operations or functionality similar to those describedherein regarding the SGW 124, although the scope of embodiments is notlimited in this respect.

In some embodiments, the network 150 may include component(s) and/ormodule(s) for functionality for a user plane function (UPF) and userplane functionality for PGW (PGW-U), as indicated by 175. In someembodiments, the network 150 may include component(s) and/or module(s)for functionality for a session management function (SMF) and controlplane functionality for PGW (PGW-C), as indicated by 180. In someembodiments, the component(s) and/or module(s) indicated by 175 and/or180 may be similar to the PGW 126 described herein, although the scopeof embodiments is not limited in this respect. The component(s) and/ormodule(s) indicated by 175 and/or 180 may perform one or more operationsor functionality similar to those described herein regarding the PGW126, although the scope of embodiments is not limited in this respect.One or both of the components 170, 172 may perform at least a portion ofthe functionality described herein for the PGW 126, although the scopeof embodiments is not limited in this respect.

Embodiments are not limited to the number or type of components shown inFIG. 1B. Embodiments are also not limited to the connectivity ofcomponents shown in FIG. 1B.

In some embodiments, a downlink resource grid may be used for downlinktransmissions from an eNB 104 to a UE 102, while uplink transmissionfrom the UE 102 to the eNB 104 may utilize similar techniques. In someembodiments, a downlink resource grid may be used for downlinktransmissions from a gNB 105 to a UE 102, while uplink transmission fromthe UE 102 to the gNB 105 may utilize similar techniques. The grid maybe a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid correspond toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element (RE). There are several different physical downlinkchannels that are conveyed using such resource blocks. With particularrelevance to this disclosure, two of these physical downlink channelsare the physical downlink shared channel and the physical down linkcontrol channel.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

FIG. 2 illustrates a block diagram of an example machine in accordancewith some embodiments. The machine 200 is an example machine upon whichany one or more of the techniques and/or methodologies discussed hereinmay be performed. In alternative embodiments, the machine 200 mayoperate as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine 200 may operatein the capacity of a server machine, a client machine, or both inserver-client network environments. In an example, the machine 200 mayact as a peer machine in peer-to-peer (P2P) (or other distributed)network environment. The machine 200 may be a UE 102, eNB 104, gNB 105,access point (AP), station (STA), user, device, mobile device, basestation, personal computer (PC), a tablet PC, a set-top box (STB), apersonal digital assistant (PDA), a mobile telephone, a smart phone, aweb appliance, a network router, switch or bridge, or any machinecapable of executing instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein, such as cloud computing, software asa service (SaaS), other computer cluster configurations.

Examples as described herein, may include, or may operate on, logic or anumber of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a machine readable medium. In an example, thesoftware, when executed by the underlying hardware of the module, causesthe hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

The machine (e.g., computer system) 200 may include a hardware processor202 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 204 and a static memory 206, some or all of which may communicatewith each other via an interlink (e.g., bus) 208. The machine 200 mayfurther include a display unit 210, an alphanumeric input device 212(e.g., a keyboard), and a user interface (UI) navigation device 214(e.g., a mouse). In an example, the display unit 210, input device 212and UI navigation device 214 may be a touch screen display. The machine200 may additionally include a storage device (e.g., drive unit) 216, asignal generation device 218 (e.g., a speaker), a network interfacedevice 220, and one or more sensors 221, such as a global positioningsystem (GPS) sensor, compass, accelerometer, or other sensor. Themachine 200 may include an output controller 228, such as a serial(e.g., universal serial bus (USB), parallel, or other wired or wireless(e.g., infrared (IR), near field communication (NFC), etc.) connectionto communicate or control one or more peripheral devices (e.g., aprinter, card reader, etc.).

The storage device 216 may include a machine readable medium 222 onwhich is stored one or more sets of data structures or instructions 224(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 224 may alsoreside, completely or at least partially, within the main memory 204,within static memory 206, or within the hardware processor 202 duringexecution thereof by the machine 200. In an example, one or anycombination of the hardware processor 202, the main memory 204, thestatic memory 206, or the storage device 216 may constitute machinereadable media. In some embodiments, the machine readable medium may beor may include a non-transitory computer-readable storage medium. Insome embodiments, the machine readable medium may be or may include acomputer-readable storage medium.

While the machine readable medium 222 is illustrated as a single medium,the term “machine readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 224. The term “machine readable medium” may include anymedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine 200 and that cause the machine 200 toperform any one or more of the techniques of the present disclosure, orthat is capable of storing, encoding or carrying data structures used byor associated with such instructions. Non-limiting machine readablemedium examples may include solid-state memories, and optical andmagnetic media. Specific examples of machine readable media may include:non-volatile memory, such as semiconductor memory devices (e.g.,Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM andDVD-ROM disks. In some examples, machine readable media may includenon-transitory machine readable media. In some examples, machinereadable media may include machine readable media that is not atransitory propagating signal.

The instructions 224 may further be transmitted or received over acommunications network 226 using a transmission medium via the networkinterface device 220 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards, a LongTerm Evolution (LTE) family of standards, a Universal MobileTelecommunications System (UMTS) family of standards, peer-to-peer (P2P)networks, among others. In an example, the network interface device 220may include one or more physical jacks (e.g., Ethernet, coaxial, orphone jacks) or one or more antennas to connect to the communicationsnetwork 226. In an example, the network interface device 220 may includea plurality of antennas to wirelessly communicate using at least one ofsingle-input multiple-output (SIMO), multiple-input multiple-output(MIMO), or multiple-input single-output (MISO) techniques. In someexamples, the network interface device 220 may wirelessly communicateusing Multiple User MIMO techniques. The term “transmission medium”shall be taken to include any intangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machine200, and includes digital or analog communications signals or otherintangible medium to facilitate communication of such software.

FIG. 3 illustrates a user device in accordance with some aspects. Insome embodiments, the user device 300 may be a mobile device. In someembodiments, the user device 300 may be or may be configured to operateas a User Equipment (UE). In some embodiments, the user device 300 maybe arranged to operate in accordance with a new radio (NR) protocol. Insome embodiments, the user device 300 may be arranged to operate inaccordance with a Third Generation Partnership Protocol (3GPP) protocol.The user device 300 may be suitable for use as a UE 102 as depicted inFIG. 1 , in some embodiments. It should be noted that in someembodiments, a UE, an apparatus of a UE, a user device or an apparatusof a user device may include one or more of the components shown in oneor more of FIGS. 2, 3, and 5 . In some embodiments, such a UE, userdevice and/or apparatus may include one or more additional components.

In some aspects, the user device 300 may include an applicationprocessor 305, baseband processor 310 (also referred to as a basebandmodule), radio front end module (RFEM) 315, memory 320, connectivitymodule 325, near field communication (NFC) controller 330, audio driver335, camera driver 340, touch screen 345, display driver 350, sensors355, removable memory 360, power management integrated circuit (PMIC)365 and smart battery 370. In some aspects, the user device 300 may be aUser Equipment (UE).

In some aspects, application processor 305 may include, for example, oneor more CPU cores and one or more of cache memory, low drop-out voltageregulators (LDOs), interrupt controllers, serial interfaces such asserial peripheral interface (SPI), inter-integrated circuit (I²C) oruniversal programmable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeinput-output (IO), memory card controllers such as securedigital/multi-media card (SD/MMC) or similar, universal serial bus (USB)interfaces, mobile industry processor interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports.

In some aspects, baseband module 310 may be implemented, for example, asa solder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board,and/or a multi-chip module containing two or more integrated circuits.

FIG. 4 illustrates a base station in accordance with some aspects. Insome embodiments, the base station 400 may be or may be configured tooperate as an Evolved Node-B (eNB). In some embodiments, the basestation 400 may be or may be configured to operate as a Next GenerationNode-B (gNB). In some embodiments, the base station 400 may be arrangedto operate in accordance with a new radio (NR) protocol. In someembodiments, the base station 400 may be arranged to operate inaccordance with a Third Generation Partnership Protocol (3GPP) protocol.It should be noted that in some embodiments, the base station 400 may bea stationary non-mobile device. The base station 400 may be suitable foruse as an eNB 104 as depicted in FIG. 1 , in some embodiments. The basestation 400 may be suitable for use as a gNB 105 as depicted in FIG. 1 ,in some embodiments. It should be noted that in some embodiments, aneNB, an apparatus of an eNB, a gNB, an apparatus of a gNB, a basestation and/or an apparatus of a base station may include one or more ofthe components shown in one or more of FIGS. 2, 4, and 5 . In someembodiments, such an eNB, gNB, base station and/or apparatus may includeone or more additional components.

FIG. 4 illustrates a base station or infrastructure equipment radio head400 in accordance with an aspect. The base station 400 may include oneor more of application processor 405, baseband modules 410, one or moreradio front end modules 415, memory 420, power management circuitry 425,power tee circuitry 430, network controller 435, network interfaceconnector 440, satellite navigation receiver module 445, and userinterface 450. In some aspects, the base station 400 may be an EvolvedNode-B (eNB), which may be arranged to operate in accordance with a 3GPPprotocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol.In some aspects, the base station 400 may be a next generation Node-B(gNB), which may be arranged to operate in accordance with a 3GPPprotocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol.

In some aspects, application processor 405 may include one or more CPUcores and one or more of cache memory, low drop-out voltage regulators(LDOs), interrupt controllers, serial interfaces such as SPI, I²C oruniversal programmable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeIO, memory card controllers such as SD/MMC or similar, USB interfaces,MIPI interfaces and Joint Test Access Group (JTAG) test access ports.

In some aspects, baseband processor 410 may be implemented, for example,as a solder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits.

In some aspects, memory 420 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magneto-resistiverandom access memory (MRAM) and/or a three-dimensional cross-pointmemory. Memory 420 may be implemented as one or more of solder downpackaged integrated circuits, socketed memory modules and plug-in memorycards.

In some aspects, power management integrated circuitry 425 may includeone or more of voltage regulators, surge protectors, power alarmdetection circuitry and one or more backup power sources such as abattery or capacitor. Power alarm detection circuitry may detect one ormore of brown out (under-voltage) and surge (over-voltage) conditions.

In some aspects, power tee circuitry 430 may provide for electricalpower drawn from a network cable to provide both power supply and dataconnectivity to the base station 400 using a single cable. In someaspects, network controller 435 may provide connectivity to a networkusing a standard network interface protocol such as Ethernet. Networkconnectivity may be provided using a physical connection which is one ofelectrical (commonly referred to as copper interconnect), optical orwireless.

In some aspects, satellite navigation receiver module 445 may includecircuitry to receive and decode signals transmitted by one or morenavigation satellite constellations such as the global positioningsystem (GPS), Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS),Galileo and/or BeiDou. The receiver 445 may provide data to applicationprocessor 405 which may include one or more of position data or timedata. Application processor 405 may use time data to synchronizeoperations with other radio base stations. In some aspects, userinterface 450 may include one or more of physical or virtual buttons,such as a reset button, one or more indicators such as light emittingdiodes (LEDs) and a display screen.

FIG. 5 illustrates an exemplary communication circuitry according tosome aspects. Circuitry 500 is alternatively grouped according tofunctions. Components as shown in 500 are shown here for illustrativepurposes and may include other components not shown here in FIG. 5 . Insome aspects, the communication circuitry 500 may be used for millimeterwave communication, although aspects are not limited to millimeter wavecommunication. Communication at any suitable frequency may be performedby the communication circuitry 500 in some aspects.

It should be noted that a device, such as a UE 102, eNB 104, gNB 105,the user device 300, the base station 400, the machine 200 and/or otherdevice may include one or more components of the communication circuitry500, in some aspects.

The communication circuitry 500 may include protocol processingcircuitry 505, which may implement one or more of medium access control(MAC), radio link control (RLC), packet data convergence protocol(PDCP), radio resource control (RRC) and non-access stratum (NAS)functions. Protocol processing circuitry 505 may include one or moreprocessing cores (not shown) to execute instructions and one or morememory structures (not shown) to store program and data information.

The communication circuitry 500 may further include digital basebandcircuitry 510, which may implement physical layer (PHY) functionsincluding one or more of hybrid automatic repeat request (HARQ)functions, scrambling and/or descrambling, coding and/or decoding, layermapping and/or de-mapping, modulation symbol mapping, received symboland/or bit metric determination, multi-antenna port pre-coding and/ordecoding which may include one or more of space-time, space-frequency orspatial coding, reference signal generation and/or detection, preamblesequence generation and/or decoding, synchronization sequence generationand/or detection, control channel signal blind decoding, and otherrelated functions.

The communication circuitry 500 may further include transmit circuitry515, receive circuitry 520 and/or antenna array circuitry 530. Thecommunication circuitry 500 may further include radio frequency (RF)circuitry 525. In an aspect of the disclosure. RF circuitry 525 mayinclude multiple parallel RF chains for one or more of transmit orreceive functions, each connected to one or more antennas of the antennaarray 530.

In an aspect of the disclosure, protocol processing circuitry 505 mayinclude one or more instances of control circuitry (not shown) toprovide control functions for one or more of digital baseband circuitry510, transmit circuitry 515, receive circuitry 520, and/or radiofrequency circuitry 525

In some embodiments, processing circuitry may perform one or moreoperations described herein and/or other operation(s). In a non-limitingexample, the processing circuitry may include one or more componentssuch as the processor 202, application processor 305, baseband module310, application processor 405, baseband module 410, protocol processingcircuitry 505, digital baseband circuitry 510, similar component(s)and/or other component(s).

In some embodiments, a transceiver may transmit one or more elements(including but not limited to those described herein) and/or receive oneor more elements (including but not limited to those described herein).In a non-limiting example, the transceiver may include one or morecomponents such as the radio front end module 315, radio front endmodule 415, transmit circuitry 515, receive circuitry 520, radiofrequency circuitry 525, similar component(s) and/or other component(s).

One or more antennas (such as 230, 312, 412, 530 and/or others) maycomprise one or more directional or omnidirectional antennas, including,for example, dipole antennas, monopole antennas, patch antennas, loopantennas, microstrip antennas or other types of antennas suitable fortransmission of RF signals. In some multiple-input multiple-output(MIMO) embodiments, one or more of the antennas (such as 230, 312, 412,530 and/or others) may be effectively separated to take advantage ofspatial diversity and the different channel characteristics that mayresult.

In some embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may be amobile device and/or portable wireless communication device, such as apersonal digital assistant (PDA), a laptop or portable computer withwireless communication capability, a web tablet, a wireless telephone, asmartphone, a wireless headset, a pager, an instant messaging device, adigital camera, an access point, a television, a wearable device such asa medical device (e.g., a heart rate monitor, a blood pressure monitor,etc.), or other device that may receive and/or transmit informationwirelessly. In some embodiments, the UE 102, eNB 104, gNB 105, userdevice 300, base station 400, machine 200 and/or other device describedherein may be configured to operate in accordance with 3GPP standards,although the scope of the embodiments is not limited in this respect. Insome embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may beconfigured to operate in accordance with new radio (NR) standards,although the scope of the embodiments is not limited in this respect. Insome embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may beconfigured to operate according to other protocols or standards,including IEEE 802.11 or other IEEE standards. In some embodiments, theUE 102, eNB 104, gNB 105, user device 300, base station 400, machine 200and/or other device described herein may include one or more of akeyboard, a display, a non-volatile memory port, multiple antennas, agraphics processor, an application processor, speakers, and other mobiledevice elements. The display may be an LCD screen including a touchscreen.

Although the UE 102, eNB 104, gNB 105, user device 300, base station400, machine 200 and/or other device described herein may each beillustrated as having several separate functional elements, one or moreof the functional elements may be combined and may be implemented bycombinations of software-configured elements, such as processingelements including digital signal processors (DSPs), and/or otherhardware elements. For example, some elements may comprise one or moremicroprocessors, DSPs, field-programmable gate arrays (FPGAs),application specific integrated circuits (ASICs), radio-frequencyintegrated circuits (RFICs) and combinations of various hardware andlogic circuitry for performing at least the functions described herein.In some embodiments, the functional elements may refer to one or moreprocesses operating on one or more processing elements.

Embodiments may be implemented in one or a combination of hardware,firmware and software. Embodiments may also be implemented asinstructions stored on a computer-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein A computer-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a computer-readable storagedevice may include read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memorydevices, and other storage devices and media. Some embodiments mayinclude one or more processors and may be configured with instructionsstored on a computer-readable storage device.

It should be noted that in some embodiments, an apparatus used by the UE102, eNB 104, gNB 105, machine 200, user device 300 and/or base station400 may include various components shown in FIGS. 2-5 . Accordingly,techniques and operations described herein that refer to the UE 102 maybe applicable to an apparatus of a UE. In addition, techniques andoperations described herein that refer to the eNB 104 may be applicableto an apparatus of an eNB. In addition, techniques and operationsdescribed herein that refer to the gNB 105 may be applicable to anapparatus of a gNB.

In accordance with some embodiments, a gNB 105 may be configurable tooperate as a master gNB (MgNB) 105. The MgNB 105 may transmitradio-resource control (RRC) signaling to provide information forconfiguring a UE 102 with a configuration for a secondary cell group(SCG) for dual connectivity to allow the UE 102 to utilize radioresources of both a master cell group (MCG) associated with the MgNB 105and the SCG. The SCG may be associated with a secondary gNB (SgNB) 105.The MgNB 105 may determine, based on inactivity of the UE 102, atransition of the UE 102 from an RRC connected mode to an RRC inactivemode. The MgNB 105 may transmit, to the SgNB 105, an SgNB releaserequest message that indicates a partial suspension of the dualconnectivity based on the transition of the UE 102 from the RRCconnected mode to the RRC inactive mode, wherein as part of the partialsuspension: a first portion of the configuration for the SCG is to bemaintained and a second portion of the configuration for the SCG is tobe released. These embodiments are described in more detail below.

FIG. 6 illustrates the operation of a method of communication inaccordance with some embodiments. It is important to note thatembodiments of the method 600 may include additional or even feweroperations or processes in comparison to what is illustrated in FIG. 6 .In addition, embodiments of the method 600 are not necessarily limitedto the chronological order that is shown in FIG. 6 . In describing themethod 600, reference may be made to one or more of FIGS. 1A, 1B, 2-5and 7-12 , although it is understood that the method 600 may bepracticed with any other suitable systems, interfaces and components.

In some embodiments, a gNB 105 may perform one or more operations of themethod 600, but embodiments are not limited to performance of the method600 and/or operations of it by the gNB 105. In some embodiments, an eNB104 configured to operate as a gNB 105 may perform one or moreoperations of the method 600 (and/or similar operations). In someembodiments, an eNB 104 may perform one or more operations of the method600 (and/or similar operations). In some embodiments, the UE 102 mayperform one or more operations of the method 600 (and/or similaroperations). Accordingly, although references may be made to performanceof one or more operations of the method 600 by the gNB 105 indescriptions herein, it is understood that the eNB 104 and/or UE 102 mayperform one or more of the same operations, in some embodiments. It isalso understood that the eNB 104 and/or UE 102 may perform one or moresimilar operations, in some embodiments. It is also understood that theeNB 104 and/or UE 102 may perform one or more reciprocal operations, insome embodiments.

In some embodiments, the gNB 105 may be arranged to operate inaccordance with a New Radio (NR) standard and/or protocol, although thescope of embodiments is not limited in this respect. While the method600 and other methods described herein may refer to eNBs 104, gNBs 105or UEs 102 operating in accordance with 3GPP standards, 5G standards, NRstandards and/or other standards, embodiments of those methods are notlimited to just those eNBs 104, gNBs 105 or UEs 102 and may also bepracticed on other devices, such as a Wi-Fi access point (AP) or userstation (STA). In addition, the method 600 and other methods describedherein may be practiced by wireless devices configured to operate inother suitable types of wireless communication systems, includingsystems configured to operate according to various IEEE standards suchas IEEE 802.11. The method 600 may also be applicable to an apparatus ofa UE 102, an apparatus of an eNB 104, an apparatus of a gNB 105 and/oran apparatus of another device described above.

It should also be noted that embodiments are not limited by referencesherein (such as in descriptions of the methods 600, 700 and 800 and/orother descriptions herein) to transmission, reception and/or exchangingof elements such as frames, messages, requests, indicators, signals orother elements. In some embodiments, such an element may be generated,encoded or otherwise processed by processing circuitry (such as by abaseband processor included in the processing circuitry) fortransmission. The transmission may be performed by a transceiver orother component, in some cases. In some embodiments, such an element maybe decoded, detected or otherwise processed by the processing circuitry(such as by the baseband processor). The element may be received by atransceiver or other component, in some cases. In some embodiments, theprocessing circuitry and the transceiver may be included in a sameapparatus. The scope of embodiments is not limited in this respect,however, as the transceiver may be separate from the apparatus thatcomprises the processing circuitry, in some embodiments.

In some embodiments, a gNB 105 configurable to operate as a master gNB(MgNB) 105 may perform one or more operations of the method 600,although the scope of embodiments is not limited in this respect. Indescriptions herein, references to an MgNB 105 and/or secondary gNB(SgNB) 105 are not limiting. Such references may be used for clarity, insome cases. In some embodiments, a gNB 105 may be configurable tooperate as an MgNB 105. In some embodiments, a gNB 105 may beconfigurable to operate as an SgNB 105. In some embodiments, a gNB 105may be configurable to operate as an MgNB 105 or as an SgNB 105. In someembodiments, a gNB 105 may be configurable to operate as an MgNB 105 andas an SgNB 105.

In some embodiments, the MgNB 105 may be arranged to operate inaccordance with a New Radio (NR) protocol and/or standard, although thescope of embodiments is not limited in this respect. In someembodiments, the SgNB 105 may be arranged to operate in accordance withan NR protocol and/or standard, although the scope of embodiments is notlimited in this respect

At operation 605, the MgNB 105 may exchange RRC signaling with a UE 102to configure dual connectivity. The RRC signaling may be included in a3GPP standard, NR standard and/or other standard, in some embodiments.It should be noted that embodiments are not limited to usage of the RRCsignaling in this operation and/or other operations described herein, asany suitable message(s) and/or signaling may be used.

In some embodiments, the MgNB 105 may transmit RRC signaling to provideconfiguration information for configuring the UE 102 with a secondarycell group (SCG) for dual connectivity to allow the UE 102 to utilizeradio resources of both a master cell group (MCG) associated with theMgNB 105 and the SCG. In some embodiments, the MgNB 105 may transmit RRCsignaling to provide information to configure the UE 102 with aconfiguration for an SCG for dual connectivity to allow the UE 102 toutilize radio resources of both an MCG associated with the MgNB 105 andthe SCG. The SCG may be associated with a secondary gNB (SgNB) 105. Insome embodiments, the MgNB 105 may transmit the RRC signaling to the UE102, although the scope of embodiments is not limited in this respect.

At operation 610, the MgNB 105 may determine whether the UE 102 isinactive. In a non-limiting example, the MgNB 105 may determineinactivity of the UE 102 based on an expiration of an RRC inactivitytimer at the MgNB 105.

At operation 615, the MgNB 105 may receive control signaling from anSgNB 105 that indicates whether the UE 102 is inactive. In someembodiments, the MgNB 105 may receive, from the SgNB, control signalingthat indicates the inactivity of the UE 102.

It should be noted that some embodiments may not necessarily include alloperations shown in FIG. 6 . In a non-limiting example, some embodimentsmay not necessarily include operation 615, and the inactivity of the UE102 may be determined by the MgNB 105 using operation 610 (and/or otheroperation(s)).

At operation 620, the MgNB 105 may determine whether the dualconnectivity is to be suspended or released. In some embodiments, theMgNB 105 may determine whether the dual connectivity is to be suspended.In some embodiments, the MgNB 105 may determine whether the dualconnectivity is to be partially suspended. In some embodiments, the MgNB105 may determine whether the dual connectivity is to be released.

In some embodiments, one or more of the following may be used: releaseof the dual connectivity, suspension of the dual connectivity, partialsuspension of the dual connectivity and/or other. In a non-limitingexample, one of the above may be used. For instance, a first embodimentmay support the partial suspension of the dual connectivity and a secondembodiments may support the release of the dual connectivity.

In some embodiments, the MgNB 105 may determine, based on inactivity ofthe UE 102, a transition of the UE 102 from an RRC connected mode to anRRC inactive mode. In some embodiments, the MgNB 105 may determine thatthe dual connectivity is to be suspended based on one or more of:detected inactivity of the UE 102, the transition of the UE 102 from anRRC connected mode to an RRC inactive mode and/or other. In someembodiments, the MgNB 105 may determine that the dual connectivity is tobe at least partially suspended based on one or more of: detectedinactivity of the UE 102, the transition of the UE 102 from an RRCconnected mode to an RRC inactive mode and/or other. In someembodiments, the MgNB 105 may determine that the dual connectivity is tobe released based on one or more of: detected inactivity of the UE 102,the transition of the UE 102 from an RRC connected mode to an RRCinactive mode and/or other.

In some embodiments, in a partial suspension of the dual connectivity, asignaling radio bearer (SRB) between the SgNB 105 and the UE 102 may bemaintained, and a data radio bearer (DRB) between the SgNB 105 and theUE 102 may be released. In some embodiments, in a partial suspension ofthe dual connectivity, a DRB between the SgNB 105 and the UE 102 may, bemaintained, and an SRB between the SgNB 105 and the UE 102 may bereleased.

In some embodiments, in a partial suspension of the dual connectivity, afirst portion of a UE context for the SgNB 105 may be maintained and asecond portion of the UE context for the SgNB 105 may be released. In anon-limiting example, the UE context may include one or more SRBs,information related to the SRBs, one or more DRBs, information relatedto the DRBs and/or other.

In some embodiments, as part of the partial suspension of the dualconnectivity: a first portion of the configuration for the SCG may bemaintained, and a second portion of the configuration for the SCG may bereleased. In a non-limiting example, the first and second portions ofthe configuration may include one or more parameters related to one ormore of: a packet data convergence protocol (PDCP) layer and a servicedata application protocol (SDAP) layer. In another non-limiting example,the first and second portions of the configuration may include one ormore parameters related to one or more of: a radio link control (RLC)layer and a medium access control (MAC) layer.

In another non-limiting example, as part of the partial suspension ofthe dual connectivity, a signaling radio bearer (SRB) between the SgNB105 and the UE 102 may be maintained and a data radio bearer (DRB)between the SgNB 105 and the UE 102 may be released.

At operation 625, the MgNB 105 may transmit an SgNB release requestmessage that indicates whether the dual connectivity is to be suspendedor released. In some embodiments, the MgNB 105 may transmit an SgNBrelease request message that indicates whether the dual connectivity isto be suspended. In some embodiments, the MgNB 105 may transmit an SgNBrelease request message that indicates whether the dual connectivity isto be released.

The SgNB release request message may be included in a 3GPP standard, NRstandard and/or other standard, in some embodiments. It should be notedthat embodiments are not limited to usage of the SgNB release requestmessage in this operation and/or other operations described herein, asany suitable message(s) and/or signaling may be used.

In some embodiments, the SgNB release request message may indicate oneor more of: a suspension of the dual connectivity, a partial suspensionof the dual connectivity, a release of the dual connectivity and/orother.

In some embodiments, the SgNB release request message may be transmittedto the SgNB 105 on an Xx interface or an Xn interface, although thescope of embodiments is not limited in this respect.

At operation 630, the MgNB 105 may transmit RRC signaling to the UE 102that indicates that the dual connectivity is suspended or released. Insome embodiments, the MgNB 105 may transmit RRC signaling to the UE 102that indicates whether the dual connectivity is suspended. In someembodiments, the MgNB 105 may transmit RRC signaling to the UE 102 thatindicates whether the dual connectivity is partially suspended. In someembodiments, the MgNB 105 may transmit RRC signaling to the UE 102 thatindicates whether the dual connectivity is released.

At operation 635, the MgNB 105 may maintain connectivity with the UE102. In some embodiments, the MgNB 105 may maintain connectivity withthe UE 102 after the dual connectivity is released. In some embodiments,the MgNB 105 may maintain connectivity with the UE 102 during thesuspension of the dual connectivity. In some embodiments, the MgNB 105may maintain connectivity with the UE 102 during the partial suspensionof the dual connectivity. In some embodiments, the MgNB 105 may maintaina configuration for the UE 102. In some embodiments, the MgNB 105 maymaintain the configuration for the UE 102 after the dual connectivity isreleased. In some embodiments, the MgNB 105 may maintain theconfiguration for the UE 102 during the suspension of the dualconnectivity. In some embodiments, the MgNB 105 may maintain theconfiguration for the UE 102 during the partial suspension of the dualconnectivity.

In some embodiments, the MgNB 105 may maintain a UE context forcommunication between the MgNB 105 and the UE 102 after the release ofthe dual connectivity. In some embodiments, the MgNB 105 may maintain aUE context for communication between the MgNB 105 and the UE 102 duringthe suspension of the dual connectivity. In some embodiments, the MgNB105 may maintain a UE context for communication between the MgNB 105 andthe UE 102 during the partial suspension of the dual connectivity.

In some embodiments, the UE context may include one or more signalingradio bearers (SRBs), information related to the SRBs, one or more dataradio bearers (DRBs), information related to the DRBs and/or other.

At operation 640, the MgNB 105 may receive, from the SgNB 105, adownlink data packet for the UE 102. At operation 645, the MgNB 105 maydetermine that the UE 102 is to be paged. At operation 650, the MgNB 105may transmit a paging message to the UE 102.

In some embodiments, the MgNB 105 may determine that the UE 102 is to bepaged based on reception of a downlink data packet from the SgNB 105 tobe forwarded to the UE 102, wherein the downlink data packet is receivedafter the release of the dual connectivity. In some embodiments, theMgNB 105 may determine that the UE 102 is to be paged based on receptionof a downlink data packet from the SgNB 105 to be forwarded to the UE102, wherein the downlink data packet is received after the suspensionof the dual connectivity. In some embodiments, the MgNB 105 maydetermine that the UE 102 is to be paged based on reception of adownlink data packet from the SgNB 105 to be forwarded to the UE 102,wherein the downlink data packet is received after the partialsuspension of the dual connectivity.

In some embodiments, the MgNB 105 may transmit a paging message to pagethe UE 102 for transmission of the downlink data packet by the MgNB 105.

At operation 655, the MgNB 105 may establish an AS security with the UE102.

At operation 660, the MgNB 105 may receive one or more measurementreports from the UE 102. At operation 665, the MgNB 105 may determinewhether dual connectivity is to be resumed. In some embodiments, theMgNB 105 may determine whether the dual connectivity established atoperation 605 is to be resumed.

In some embodiments, the one or more measurement reports may be receivedfrom the UE 102 during the partial suspension of the dual connectivity.In some embodiments, the one or more measurement reports may be receivedfrom the UE 102 during the suspension of the dual connectivity. In someembodiments, the one or more measurement reports may be received fromthe UE 102 after the release of the dual connectivity.

In some embodiments, the one or more measurement reports may includeinformation related to the SgNB 105 and/or the dual connectivity. In anon-limiting example, a measurement report may include a signal qualitymeasurement for the SgNB 105 at the UE 102. In some embodiments, theMgNB 105 may determine whether the dual connectivity is to be resumedwith the SgNB 105 based on one or more of: signal quality measurement(s)for the SgNB, measurement reports and/or other.

Example signal quality measurements include, but are not limited to,signal-to-noise ratio (SNR), reference signal received power (RSRP),reference signal received quality (RSRQ), and received signal strengthindicator (RSSI).

In some embodiments, the MgNB 105 may determine whether the dualconnectivity is to be resumed with the SgNB 105 based on one or moremeasurement reports received from the UE, wherein: the measurementreports received from the UE 102 after the AS security is establishedare used for the determination, and the measurement reports receivedfrom the UE 102 before the AS security is established are not used forthe determination.

In some embodiments, the MgNB 105 may receive a message (including butnot limited to a message 3 (Msg-3) of a 3GPP protocol and/or NRprotocol) that includes information related to connectivity of the UE102 and/or location of the UE 102. In a non-limiting example, themessage may be received after the dual connectivity has been suspended,partially suspended or released. In some embodiments, the message may bea Msg-3. In some embodiments, the message may be a message receivedafter a Msg-3.

The MgNB 105 may determine, based at least partly on the informationrelated to connectivity of the UE 102 and/or location of the UE 102,whether the dual connectivity is to be resumed with the SgNB 105. Insome embodiments, the information related to connectivity of the UE 102and/or location of the UE 102 may include one or more of: whether the UE102 is in a cell in which a UE context is stored, whether the UE 102 isin a same location as during a previous communication with the MgNB 105,whether the SCG for the dual connectivity is valid and/or otherinformation.

At operation 670, the MgNB 105 may transmit RRC signaling to the UE thatindicates whether dual connectivity is to be resumed. In someembodiments, the MgNB 105 may transmit the RRC signaling to indicatewhether the dual connectivity established at operation 605 is to beresumed.

In some embodiments, the MgNB 105 may transmit, to the UE 102, a message(including but not limited to a message 4 (Msg-4) of a 3GPP protocoland/or NR protocol)) that indicates whether the dual connectivity is tobe resumed with the SgNB 105. In some embodiments, the message may beencoded in accordance with the AS security, although the scope ofembodiments is not limited in this respect. In some embodiments, themessage may be a Msg-4. In some embodiments, the message may be amessage transmitted after a Msg-4.

Some of the messages and/or signaling described herein may be includedin a standard and/or protocol, including but not limited to ThirdGeneration Partnership Project (3GPP), 3GPP Long Term Evolution (LTE).Fourth Generation (4G), Fifth Generation (5G), New Radio (NR) and/orother. The scope of embodiments is not limited to usage of elements thatare included in standards, however.

In some embodiments, an apparatus of the MgNB 105 may comprise memory.The memory may be configurable to store at least a portion of the SgNBrelease request message. The memory may store one or more other elementsand the apparatus may use them for performance of one or moreoperations. The apparatus may include processing circuitry, which mayperform one or more operations (including but not limited tooperation(s) of the method 600 and/or other methods described herein).The processing circuitry may include a baseband processor. The basebandcircuitry and/or the processing circuitry may perform one or moreoperations described herein, including but not limited to encoding ofthe SgNB release request message. The apparatus may include atransceiver to transmit the SgNB release request message. Thetransceiver may transmit and/or receive other blocks, messages and/orother elements.

FIG. 7 illustrates the operation of another method of communication inaccordance with some embodiments. FIG. 8 illustrates the operation ofanother method of communication in accordance with some embodiments.Embodiments of the methods 700 and 800 may include additional or evenfewer operations or processes in comparison to what is illustrated inFIGS. 7-8 and embodiments of the methods 700 and/or 800 are notnecessarily limited to the chronological order that is shown in FIGS.7-8 . In describing the methods 700 and/or 800, reference may be made toone or more of the figures described herein, although it is understoodthat the methods 700 and/or 800 may be practiced with any other suitablesystems, interfaces and components. In addition, embodiments of themethods 700 and/or 800 may be applicable to UEs 102, eNBs 104, gNBs 105,APs, STAs and/or other wireless or mobile devices. The methods 700and/or 800 may also be applicable to an apparatus of a UE 102, eNB 104,gNB 105 and/or other device described above.

In some embodiments, a gNB 105 (including but not limited to a gNB 105configurable to operate as an SgNB 105) may perform one or moreoperations of the method 700, but embodiments are not limited toperformance of the method 700 and/or operations of it by the SgNB 105.In some embodiments, the eNB 104 and/or UE 102 may perform one or moreoperations of the method 700 (and/or similar operations). Althoughreferences may be made to performance of one or more operations of themethod 700 by the SgNB 105 in descriptions herein, it is understood thatthe MgNB 105, eNB 104 and/or UE 102 may perform: one or more of the sameoperations; one or more similar operations; and/or one or morereciprocal operations, in some embodiments.

In some embodiments, a UE 102 may perform one or more operations of themethod 800, but embodiments are not limited to performance of the method800 and/or operations of it by the UE 102. In some embodiments, the eNB104, MgNB 105, SgNB 105 and/or gNB 105 may perform one or moreoperations of the method 800 (and/or similar operations). Althoughreferences may be made to performance of one or more operations of themethod 800 by the UE 102 in descriptions herein, it is understood thatthe eNB 104, MgNB 105, SgNB 105 and/or gNB 105 may perform: one or moreof the same operations; one or more similar operations; and/or one ormore reciprocal operations, in some embodiments.

It should be noted that one or more operations of one of the methods600, 700, 800 may be the same as, similar to and/or reciprocal to one ormore operations of the other methods. For instance, an operation of themethod 600 may be the same as, similar to and/or reciprocal to anoperation of the method 700, in some embodiments. In a non-limitingexample, an operation of the method 600 may include transmission of anelement (such as a frame, block, message and/or other) from MgNB 105 tothe SgNB 105, and an operation of the method 700 may include receptionof a same element (and/or similar element) from the MgNB 105 by the SgNB105. In some cases, descriptions of operations and techniques describedas part of one of the methods 600, 700, 800 may be relevant to one orboth of the other methods.

In addition, previous discussion of various techniques and concepts maybe applicable to the methods 700 and/or 800 in some cases, including butnot limited to dual connectivity, suspension of dual connectivity,partial suspension of dual connectivity, release of dual connectivity,MgNB 105. SgNB 105, SCG, MCG, Xn interface, Xx interface, messages(including but not limited to messages described regarding the method600) and/or other. In addition, the examples shown in one or more of thefigures may also be applicable, in some cases, although the scope ofembodiments is not limited in this respect.

In some embodiments, a gNB 105 configurable to operate as an SgNB 105may perform one or more operations of the method 700, although the scopeof embodiments is not limited in this respect. In some embodiments, theSgNB 105 may be arranged to operate in accordance with a New Radio (NR)protocol and/or standard, although the scope of embodiments is notlimited in this respect.

At operation 705, the SgNB 105 may exchange control signaling with theMgNB 105 to configure dual connectivity. In some embodiments, the SgNB105 may receive, from the MgNB 105, control signaling that includesconfiguration information for configuring a UE 102 with a secondary cellgroup (SCG) for dual connectivity to allow the UE 102 to utilize radioresources of both a master cell group (MCG) associated with the MgNB 105and the SCG. The SCG may be associated with the SgNB 105.

At operation 710, the SgNB 105 may determine whether the UE 102 isinactive. In some embodiments, the SgNB 105 may determine whether the UE102 is to be put into an inactive mode. In a non-limiting example, theSgNB 105 may determine, based on a time duration elapsed since aprevious uplink communication from the UE 102, whether the UE 102 isinactive. In another non-limiting example, the SgNB 105 may determine,based on a time duration elapsed since a previous uplink communicationfrom the UE 102, whether the UE 102 is to be put into the inactive mode.

At operation 715, the SgNB 105 may transmit control signaling to theMgNB to indicate that the UE is inactive. In some embodiments, thecontrol signaling may be transmitted on an Xx or an Xn interface betweenthe SgNB 105 and the MgNB 105, although the scope of embodiments is notlimited in this respect.

It should be noted that some embodiments may not necessarily include alloperations shown in FIG. 7 . In a non-limiting example, some embodimentsmay not necessarily include operations 710-715, and the inactivity ofthe UE 102 may be determined by the MgNB 105.

At operation 720, the SgNB 105 may receive an SgNB release requestmessage. At operation 725, the SgNB 105 may release a first portion ofthe SCG. At operation 730, the SgNB 105 may maintain a second portion ofthe SCG.

In some embodiments, the SgNB 105 may receive, from the MgNB 105, anSgNB release request message that indicates a partial suspension of thedual connectivity, wherein: a data radio bearer (DRB) between the SgNB105 and the UE 102 is to be released, and a signaling radio bearer (SRB)between the SgNB 105 and the UE 102 is to be maintained.

In some embodiments, the SgNB release request message may be received onan Xx or an Xn interface between the SgNB 105 and the MgNB 105, althoughthe scope of embodiments is not limited in this respect.

At operation 735, the SgNB 105 may receive, from the SGW 124, a downlinkdata packet for the UE 102. At operation 740, the SgNB 105 may forwardthe downlink data packet to the MgNB 105.

In some embodiments, the downlink data packet received at operation 735may be received during a partial suspension of the dual connectivity. Insome embodiments, the downlink data packet received at operation 735 maybe received during a suspension of the dual connectivity. In someembodiments, the downlink data packet received at operation 735 may bereceived after a release of the dual connectivity.

In some embodiments, an apparatus of the SgNB 105 may comprise memory.The memory may be configurable to store information related to theinformation related to the SgNB release request message. The memory maystore one or more other elements and the apparatus may use them forperformance of one or more operations. The apparatus may includeprocessing circuitry, which may perform one or more operations(including but not limited to operation(s) of the method 700 and/orother methods described herein). The processing circuitry may include abaseband processor. The baseband circuitry and/or the processingcircuitry may perform one or more operations described herein, includingbut not limited to decoding of the SgNB release request message. Theapparatus may include a transceiver to receive the SgNB release requestmessage. The transceiver may transmit and/or receive other blocks,messages and/or other elements.

At operation 805, the UE 102 may exchange RRC signaling with the MgNB105 to configure dual connectivity. At operation 810, the UE 102 mayreceive RRC signaling that indicates that the dual connectivity issuspended or released. At operation 815, the UE 102 may receive a pagingmessage from the MgNB 105. At operation 820, the UE 102 may receive adownlink data packet from the MgNB 105. At operation 825, the UE 102 maydetermine a signal quality measurement for the SgNB 105. At operation830, the UE 102 may establish an AS security with the MgNB 105. Atoperation 835, the UE 102 may transmit a measurement report to the MgNB105. At operation 840, the UE 102 may receive RRC signaling to the UEthat indicates whether dual connectivity is to be resumed.

It should be noted that in descriptions herein of one or moreoperations, methods and/or techniques, the UE 102 may exchangesignaling, messages, packets and/or other elements with the MgNB 105.Such references are not limiting, however. In some embodiments, the UE102 may exchange the same or similar signaling, messages, packets and/orother elements with other base station components. For instance, such abase station component may be configured to operate in accordance withan Evolved Universal Terrestrial Radio Access (E-UTRA) New Radio DualConnectivity (EN-DC) technique/protocol/standard.

In some embodiments, the MgNB 105 may operate in accordance with an NRtechnique/protocol and a secondary eNB (SeNB) 104 may operate inaccordance with an LTE technique/protocol. This may be in accordancewith an NR EUTRA (NE-DC) arrangement, although the scope of embodimentsis not limited in this respect.

In some embodiments, the UE 102 may receive, from the MgNB 105, firstRRC signaling that includes configuration information for configuringthe UE 102 with a secondary cell group (SCG) for dual connectivity toallow the UE 102 to utilize radio resources of both a master cell group(MCG) associated with the MgNB 105 and the SCG. The SCG may beassociated with the SgNB 105. The UE 102 may receive, from the MgNB 105,second RRC signaling that indicates a suspension of the dualconnectivity. The UE 102 may, during the suspension of the dualconnectivity: monitor for paging messages from the MgNB; determine asignal quality measurement based on a downlink signal received from theSgNB 105; transmit, to the MgNB 105, a measurement report that indicatesthe signal quality measurement; and/or other operation(s).

In some embodiments, the UE 102 may receive control signaling from theMgNB 105 for an establishment of an access stratum (AS) security. Insome embodiments, the UE 102 may encode the measurement report inaccordance with the AS security, although the scope of embodiments isnot limited in this respect.

In some embodiments, the UE 102 may be configured with a first mediumaccess control (MAC) entity for the MCG, and the UE 102 may beconfigured with a second MAC entity for the SCG. In some embodiments,the UE 102 may be configured with the first and second MAC entities aspart of the dual connectivity, although the scope of embodiments is notlimited in this respect.

In some embodiments, as part of the partial suspension of the dualconnectivity, the UE 102 may maintain a first portion of theconfiguration for the SCG and may release a second portion of theconfiguration for the SCG. In a non-limiting example, the first andsecond portions of the configuration may include one or more parametersrelated to one or more of: a packet data convergence protocol (PDCP)layer and a service data application protocol (SDAP) layer. In anothernon-limiting example, the first and second portions of the configurationmay include one or more parameters related to one or more of: a radiolink control (RLC) layer and a medium access control (MAC) layer.

In another non-limiting example, as part of the partial suspension ofthe dual connectivity, a signaling radio bearer (SRB) between the SgNB105 and the UE 102 may be maintained and a data radio bearer (DRB)between the SgNB 105 and the UE 102 may be released.

In some embodiments, an apparatus of the UE 102 may comprise memory. Thememory may be configurable to store a signal quality measurement. Thememory may store one or more other elements and the apparatus may usethem for performance of one or more operations. The apparatus mayinclude processing circuitry, which may perform one or more operations(including but not limited to operation(s) of the method 800 and/orother methods described herein). The processing circuitry may include abaseband processor. The baseband circuitry and/or the processingcircuitry may perform one or more operations described herein, includingbut not limited to decoding of RRC signaling. The apparatus may includea transceiver to receive RRC signaling. The transceiver may transmitand/or receive other blocks, messages and/or other elements.

FIG. 9 illustrates example operations in accordance with someembodiments. FIG. 10 illustrates additional example operations inaccordance with some embodiments. FIG. 11 illustrates additional exampleoperations in accordance with some embodiments. It should be noted thatthe examples shown in FIGS. 9-11 may illustrate some or all of theconcepts and techniques described herein in some cases, but embodimentsare not limited by the examples. For instance, embodiments are notlimited by the name, number, type, size, ordering, arrangement and/orother aspects of the operations, messages, gNBs 105, UEs 102, and otherelements as shown in FIGS. 9-11 . Although some of the elements shown inthe examples of FIGS. 9-11 may be included in a 3GPP LTE standard, 5Gstandard, NR standard and/or other standard, embodiments are not limitedto usage of such elements that are included in standards.

In some embodiments, a method may enable the resumption, suspensionand/or RAN-initiated paging of UEs 102 that were configured with DualConnectivity (DC) while they were in connected mode.

In some embodiments, the DC configuration may be released. When a UE 102enters an inactive mode, an SgNB 105 configuration and configured SgNBbearers may be released. In some cases, this technique may be considereda baseline mechanism, although the scope of embodiments is not limitedin this respect.

In some embodiments, the DC configuration may be suspended. When the UE102 enters the inactive mode, the UE 102 may keep an SCG configurationand an MCG configuration. It is also possible that a first portion of aconfiguration may be suspended and a second portion of the configurationmay be released. In a non-limiting example, an SCG DRB configuration maybe kept while other remaining SCG configuration may be released. In somecases, this technique may be considered an improved/optimized mechanism(such as in comparison to the baseline mechanism described above),although the scope of embodiments is not limited in this respect.

It should be noted that techniques, operations and/or methods describedherein may use exemplary names or references, but the scope ofembodiments is not limited by such exemplary names and references. Insome embodiments, one or more of the techniques, operations and/ormethods described herein may be applicable to the suspension orinactivation mechanism, as well as to the resumption or activationmechanism. In some embodiments, one or more of the techniques,operations and/or methods described herein may be applicable to NR, LTE,as well as other technologies. In some embodiments, one or more of thetechniques, operations and/or methods described herein may be applicableto a state or sub-state defined for a UE suspended or inactive that maybe referred to as inactive, light connection and/or similar. In someembodiments, one or more of the techniques, operations and/or methodsdescribed herein may be applicable to Xn or Xx signalling, and may alsobe applicable to other CN signaling, such as signaling over interfaceN2/N3 or X2 or S1. In some embodiments, one or more of the techniques,operations and/or methods described herein may be applicable to enableDC between two nodes that may be referred to as MgNB and SgNB, oralternatively MCG and SCG, or in another different way.

In some cases, descriptions herein of a message, technique, operationand/or method may refer to an MgNB 105, but such references are notlimiting. In some cases, the message, technique, operation and/or methodmay be applicable to an MeNB 104, eNB 104, gNB 105 and/or other device,in some embodiments. In a non-limiting example, an MeNB 104 may be usedinstead of an MgNB 105, in some embodiments. In another non-limitingexample, a message label, message contents, message function and/orother aspect may refer to an MgNB 105, but a same message and/or similarmessage (in terms of message label, message contents, message functionand/or other aspect) may be used for an MeNB 104, in some embodiments.

Similarly, in some cases, descriptions herein of a message, technique,operation and/or method may refer to an SgNB 105, but such referencesare not limiting. In some cases, the message, technique, operationand/or method may be applicable to an SeNB 104, eNB 104, gNB 105 and/orother device, in some embodiments.

In some embodiments, in accordance with NR operation, non-limitingexamples of Dual Connectivity (DC) use cases are given in the tablebelow. In some embodiments, one or more additional use cases may bepossible. In some embodiments, one or more of the use cases in the tablebelow may not necessarily be included.

Options MgNB SgNB CN #0 NR-DC NR-RAN NR-RAN 5GC #3 EN-DC RAN NR-RAN EPC#7 NGEN-DC RAN NR-RAN 5GC #4 NE-DC NR-RAN RAN 5GC

In some embodiments, a DC configuration may be released when the UE 102enters an inactive mode. For instance, an SgNB 105 configuration andconfigured SgNB bearers may be released. For this technique (release ofthe DC configuration), one or more of the following may be applicable,although the scope of embodiments is not limited in this respect. Insome cases, RAN-initiated paging mechanism may not necessarily beimpacted (as DL data is received by MgNB). In some cases, one or moreexisting procedures may be used. In some cases, DC may be released dueto inactivity even before UE 102 is put into the inactive mode.

In some cases, potentially unnecessary signaling (such as signaling overRAN and CN interfaces) may be generated for the suspension andresumption cases in which the UE 102 may not have changed its location.The reason is that upon suspension of the UE 102, the MgNB 105 maynotify the SgNB 105 that the UE 102 enters into the inactive mode (whichmay trigger the release of the SgNB configuration/bearers). However,after resumption, if the UE 102 is still in the same cell/location, theMgNB 105 may want to enable again the SgNB configuration/bearers. Hencea transition to the inactive mode may no longer be transparent to theCN.

In some embodiments, techniques to reduce a number of messages may beused, such as combining of reconfiguration and release.

In some embodiments, a DC configuration may be suspended when the UE 102enters an inactive mode. For instance, the UE 102 may keep the SCGconfiguration and/or the MCG configuration. In this approach, it is alsopossible that only a part of SCG configuration may be suspended and oneor more other parts may be released (which may be similar to techniquesused for the DC configuration on LTE re-establishment, although thescope of embodiments is not limited in this respect). For instance, theDRB configuration may be kept while other remaining SCG configurationmay be released.

For this technique (suspension of the DC configuration), one or more ofthe following may be applicable, although the scope of embodiments isnot limited in this respect. In some cases, a savings of signaling (forinstance, signaling over RAN and CN interfaces) may result for thesuspension and resumption cases in which the UE 102 has not changed itslocation (for instance, a same RAN area, such as a cell, in which the UEAS context is stored). In some cases, potentially unnecessary signaling(for instance, signaling over RAN and CN interfaces) may result for thesuspension and resumption cases in which the UE 102 has changed itslocation to a different RAN area in which the UE AS context is notstored. In some cases, a RAN-initiated paging mechanism may be impacted(as DL data is received by SgNB 105 when the RAN-initiated paging ishandled by the MgNB 105) and additional CN signaling may result.

For this technique (suspension of the DC configuration), one or more ofthe following may be applicable, although the scope of embodiments isnot limited in this respect. In some cases, upon resumption for mobileterminating case, DL Data forwarding handling in SgNB 105 may berequired for UEs 102 in an inactive mode if the UE 102 has changed itslocation to a different RAN area (such as a cell) in which the UE AScontext is not stored. It should be noted that for an MCG split bearer,this may not be needed (for instance, if the PDCP is located in theMCG).

For this technique (suspension of the DC configuration), one or more ofthe following may be applicable, although the scope of embodiments isnot limited in this respect. In some cases, an update of resumptionprocedure may be performed to enable the reconfiguration of SgNB 105.Some indication from the UE 102 on whether the current SgNB or anotherSgNB is suitable may be used. Measurement reporting for this may need aninitiation of AS security, which may result in a multi-step approachwherein security is first activated, measurement results are received,and SN is configured. The DRBs (at least the split and SCG DRBs) mayremain suspended during this period. In comparison to other techniques,an increase in signaling over the radio may result, although CNsignaling may be reduced if the UE 102 has not moved. The UE 102 may beasked to perform measurements on NR so it has results ready to provideif requested. In some embodiments, as a potentialimprovement/optimization, an indication that the current SgNB 105 isstill suitable in Resume request from the UE 102 can be considered.Since this does not involve measurement reports, it can be sentunencrypted in some cases. In some cases, a procedure to activatesecurity and obtain measurement reports may only be needed if UE 102 hasmoved.

For this technique (suspension of the DC configuration), one or more ofthe following may be applicable, although the scope of embodiments isnot limited in this respect. In some cases, if the UE 102 has not moved,the current SCG configuration may be resumed. If the UE 102 has moved, aprocedure that combines parts of inter-gNB resume, MN HO and SN changemay be used to move the UE contexts to the new MN and SN along with anydata forwarding.

In some embodiments, the MgNB 105 may need to know whether the SgNBconfiguration is valid/applicable or not for a given UE 102. In someembodiments, the UE 102 may report measurements. In some cases, the ASsecurity may need to be resumed before the measurements can be provided.In some embodiments, the UE 102 may report information. The UE 102 mayprovide location information of the UE 102 that may enable the gNB 105to determine one or more of: whether the UE 102 is still in the samecell/location as indicated in the UE AS Context (that is, the same asbefore suspension of the RRC Connection); whether the SgNB configurationis still suitable; and/or other. In some embodiments, the locationinformation from the UE 102 may be conveyed within MSG3 (such as an RRCConnection Resume Request message and/or other). In some embodiments,the location information from the UE 102 may include one or more flags,one or more bits and/or other, which may be used to indicate informationsuch as: if the UE 102 and RAN are synchronized; the location/cell towhich the information refers; and/or other.

Regarding the location of the UE 102, different scenarios are possible.In some cases in which the UE 102 is in the inactive mode has not movedfrom its previous location/cell, for the resumption mechanism: uponMSG4, the MgNB 105 may reconfigure one or more of the MgNB or SgNBconfigurations or bearers. In some cases in which the UE 102 is in theinactive mode and has moved from its previous location/cell, theresumption mechanism may be updated, and at least the following optionsare possible.

In a first option, AS security may be enabled/resumed andreconfiguration may be performed. For instance, the resumption mayenable/resume the AS security and the reconfiguration may enable/resumesome or all bearers at the same time. Partial resumption of MgNB bearersmay be done while resuming (via MSG4) while SgNB bearers/configurationmay be resumed afterwards. In a second option, an RRC message 4 may besent by the RAN node encrypted or unencrypted (which may depend onwhether the NCC key and potentially encryption algorithm needs to beupdated).

In some embodiments, when the UE 102 enters the inactive mode,configured bearers may be reconfigured to MCG bearers as DCconfiguration is released. In some cases, this may be performed by UEautonomous reconfigure bearer to MCG bearer. In some cases, the MgNB mayperform explicit reconfiguration before sending the UE 102 to theinactive mode. In some cases, the UE 102 and the network side may needto be aware the DC configuration is released. In the above, the networkside may include one or more RAN nodes (for instance. MgNB 105 and SgNB105) and may include one or more CN nodes (for instance, AMF or UPF).

In some embodiments, the MgNB 105 may be use an MgNB initiated SgNB/SeNBrelease procedure to inform SgNB/SeNB to release the SCG configuration.An example of such a procedure based on the LTE DC is shown in FIG. 9 .

In some embodiments, CN signaling between the MgNB 105 and SgNB 105 maybe used to notify and potentially even confirm the release of the DCconfiguration. In a non-limiting example, signaling that is included ina procedure (including but not limited to release or reconfiguration)may be used. For instance. Xn or Xx signaling may be used as SeNBRelease Request may be required for Option 0 and 4 (with one or moremessages related to hand shake). One or more Xn messages for the MgNB105 to coordinate with SgNB/SeNB when the UE 102 enters the inactivemode may be used, in some embodiments.

In some embodiments, the SgNB 105 may inform the MgNB 105 when the UPpath is not active. A “user inactivity” cause value may be used, forinstance in the SeNB initiated SeNB Modification. A non-limiting exampleof the user inactivity field is given below.

User The action is requested due to user inactivity on all E- InactivityRABs, e.g., S1 is requested to be released in order to optimise theradio resources; or SeNB didn't see activity on the DRB recently. Incurrent version of this specification applicable for Dual Connectivityonly

In some embodiments, CN signaling may be exchanged between the MgNB 105and SgNB 105 to notify and potentially even confirm when user inactivityis triggered and when the suspension is done. In a non-limiting example,signaling that is included in a procedure (including but not limited tomodification, release or reconfiguration) may be used. For instance, Xnor Xx signaling related to SeNB initiated SeNB Modification message(with one or more messages related to hand shake) may be used. One ormore Xn messages may be used for the SeNB 105 to inform the MeNB whensuspension of the RRC connection could be considered due to certain datainactivity.

In some embodiments, on the RRC level, the following options arepossible on how to handle the SgNB release while moving the connected UE102 to the inactive mode. In a first option, the MgNB 105 may transmitan RRC connection reconfiguration message that includes the informationto release SCG configuration and may transmit an RRC connection releasemessage to inform the UE 102 of its transition into the inactive mode.In a second option, the MgNB 105 may transmit an RRC connection releasemessage that informs the UE 102 of the release of the SCG configuration(implicitly or explicitly) and further informs the UE 102 of itstransition into the inactive mode.

In some embodiments, when the UE 102 enters the inactive mode, the UE102 may keep the SgNB configuration and the MgNB configuration. Anindication to notify when the UE 102 enters or exits the inactive modemay be sent by the MgNB 105. For instance, the MgNB 105 may inform theSgNB 105 when the UE 102 enters and exits from the inactive mode toenable the SgNB 105 to know and/or determine when to notify the MgNB 105and buffer incoming DL data. In some cases, CN signaling may be usedbetween the MgNB 105 and the SgNB 105 to notify when the UE 102enters/exits from the inactive mode. In some embodiments, the signalingmay be based on one or more procedures (including but not limited torelease or reconfiguration). For instance, Xn or Xx signaling may beused. In some embodiments, one or more messages related to hand shakemay be used. In some embodiments, one or more Xn messages may be usedfor the MgNB 105 to coordinate with SgNB 105 when a UE 102 enters theinactive mode or exits the inactive mode. In a non-limiting example, 2or 4 such messages may be used.

In some embodiments, a trigger from SgNB 105 of RAN-initiated paging maybe required and/or used when new DL data reaches the SgNB 105/SeNB 104.The MgNB 105 may control the RAN-initiated paging within the RNA,therefore SgNB 105/SeNB 104 may need to inform the MgNB 105 when new DLdata is received for a UE 102 that is in the inactive mode.Alternatively, the RAN-initiated paging may be fully or partiallycontrolled by the SgNB 105 for UEs 102 in the active mode.

In some embodiments, CN signaling between the MgNB 105 and SgNB 105 maybe used to notify when new DL data arrives for a given UE 102 in theinactive mode. This signaling may be related to a procedure (includingbut not limited to release or reconfiguration). For instance, Xn or Xxsignaling may be used. In some embodiments, one or more message relatedto hand shake may be used. In some embodiments, one or more Xn messagesmay be sent by the SgNB 105/SeNB 104 to inform the MgNB 105 when new DLdata arrives for a UE 102 in the inactive mode. In a non-limitingexample, for MO access, two or four Xn messages may be used. In anothernon-limiting example, for MT access, four or six Xn messages may beused.

In some embodiments, while the UE 102 is in a connected mode (includingbut not limited to RRC_CONNECTED), the SgNB 105 may inform the MgNB 105when suspension of the RRC connection could be considered due to certaindata inactivity. In some embodiments, data forwarding from SgNB 105/SeNB104 may need to be enabled over the network interfaces (such as Xn, Xx.NG-c and/or other). In some embodiments, if no MgNB 105 and SgNB105/SeNB 104 change during a transition of the UE 102 from an inactivemode to an active mode, data forwarding may not necessarily be needed.

In some embodiments, if no MgNB 105 change occurs but a change of SgNB105/SeNB 104 during the transition of the UE 102 from the inactive modeto the active mode, there may be a need to perform a procedure (such asan LTE DC follow procedure, similar procedure and/or other procedure)during the resumption of the RRC Connection. An example of such aprocedure is illustrated in FIG. 10 .

In some embodiments, if a change of MgNB 105 occurs but no change ofSgNB 105/SeNB 104 occurs during the transition of the UE 102 from theinactive mode to the active mode, there may be a need to perform aprocedure (such as an LTE DC follow procedure, similar procedure and/orother procedure) during the resumption of the RRC Connection. An exampleof such a procedure is illustrated in FIG. 11 .

In some embodiments, if there is a change in both the MgNB 105 and theSgNB 105/SeNB 104 during the transition of the UE 102 from the inactivemode to the active mode, a procedure may be performed. In a non-limitingexample, the procedure may be similar to one of the procedures in FIG.10 or FIG. 11 , except that the SgNB Addition procedure may be performedwith a new SgNB 105 and further data forwarding from the S-SgNB 105 tothe T-SgNB 105 may be performed.

In some embodiments, instead of suspension of all of a DC configuration,one part of it may be suspended and another part may be released. In anon-limiting example, a procedure may be used, wherein the procedure maybe similar to a procedure performed in LTE with the DC configuration onLTE re-establishment. In the LTE re-establishment procedure, the SCGconfiguration may be released but the DRB configuration for the DRB Typemay be maintained upon RRC connection re-establishment. For instance,the following (or similar) may be performed: release the entire SCGconfiguration, if configured, except for the DRB configuration (asconfigured by drb-ToAddModListSCG). In some embodiments, this may bemaintained until the first RRC Connection Reconfiguration message inwhich the SgNB 105 may configure accordingly on whether to continuemaintaining the DRB type or to reconfigure them to other DRB type (forinstance, an MCG bearer). In some embodiments, if a similar mechanismwere enabled for the inactive mode, the gNB 105 may indicate via RACHMSG4 (such as RRCConnectionResume and/or other) the desirablereconfiguration. For instance, the message may indicate whether tocontinue maintaining the DRB type or to reconfigure them to another DRBtype. In some embodiments, this may be an autonomous release of theconfiguration by the UE 102 (for instance, the MgNB 105 and SgNB 105 maystill keep the configuration. In some cases, the SgNB configuration thatis released when the UE 102 enters the inactive mode may be provided.

In some cases, a signaling trade-off may be realized (when a UE entersan inactive mode) between a first approach, wherein a DC configurationis released and other approaches, wherein some level of DC configurationis kept. For instance, a trade-off between two or more of the followingmay be realized: potential (de)configuration of DC in some (or all)CONNECTED/INACTIVE transmission, additional Xn signaling to handle thesuspension of DC in some (or all) CONNECTED/INACTIVE transmission,update(s) of RAN-initiated paging and/or other.

In some embodiments, one or more techniques (including but not limitedto the techniques described herein) may enable resumption, suspensionand RAN-initiated paging of UEs 102 that were configured with DualConnectivity (DC) while they were in an RRC connected mode. In someembodiments, the DC configuration may be released. In some embodiments,CN signaling (such as Xn or Xx) between the MgNB 105 and SgNB 105 may beused to notify and potentially confirm the release of the DCconfiguration. In some embodiments. CN signaling (such as Xn or Xx)between the MgNB 105 and SgNB 105 may be used to notify and potentiallyconfirm user inactivity which may trigger the suspension of the RRCconnection. In some embodiments, RRC signaling between the MgNB 105 andUE 102 may be used to notify of the SCG configuration.

In some embodiments, one or more techniques (including but not limitedto the techniques described herein) may enable resumption, suspensionand RAN-initiated paging of UEs 102 that were configured with DualConnectivity (DC) while they were in an RRC connected mode. In someembodiments, the DC configuration may be suspended or deactivated. Insome embodiments, part of the DC configuration (such as DRBconfiguration associated with the SCG) may be suspended or de-activatedand another part of the DC configuration (such as the remaining SCGconfiguration) may be released. In some embodiments, CN signaling (suchas Xn or Xx) between the MgNB 105 and SgNB 105 may be used to notifywhen a UE 102 enters and/or exits from an RRC inactive mode. In someembodiments, CN signaling (such as Xn or Xx) between the MgNB 105 andSgNB 105 may be used to notify when new DL data arrives to the SgNB 105for a UE 102 in an RRC inactive mode. In some embodiments, CN signaling(such as Xn or Xx) between the MgNB 105 and SgNB 105 may be used tonotify and potentially confirm of the user inactivity which may triggerthe suspension of an RRC connection. In some embodiments, a mechanism toenable data forwarding from an SgNB 105 may be used.

In some embodiments, one or more techniques (including but not limitedto the techniques described herein) may enable resumption, suspensionand RAN-initiated paging of UEs 102 that were configured with DualConnectivity (DC) while they were in an RRC connected mode. In someembodiments, the UE 102 in an RRC inactive mode may provide informationof the DC configuration (such as to the MgNB 105 and/or othercomponent(s)). In some embodiments, the UE 102 may send one or moremeasurement reports after resuming an AS security. In some embodiments,some or all of the information provided by the UE 102 during theresumption, such as information included in MSG3 and/or othermessage(s), to determine if a DC configuration is applicable. In someembodiments, the information provided by the UE 102 may indicate one ormore of: that the UE 102 is on a same cell in which the UE AS Context isstored, that the UE 102 is in a same location (as a previous location),that an SCG configuration is still applicable and/or other information.In some embodiments, a resumption procedure may include one or more of:resuming the AS security, providing the reconfiguration informationand/or other. In some embodiments, in a resumption procedure, a message(including but not limited to an RRC message 4) may be sent by the RANnode encrypted or unencrypted.

In Example 1, a generation Node-B (gNB) may be configurable to operateas a master gNB (MgNB). An apparatus of the gNB may comprise memory. Theapparatus may further comprise processing circuitry. The processingcircuitry may be configured to encode radio-resource control (RRC)signaling to provide information for configuring a User Equipment (UE)with a configuration for a secondary cell group (SCG) for dualconnectivity to allow the UE to utilize radio resources of both a mastercell group (MCG) associated with the MgNB and the SCG, the SCGassociated with a secondary gNB (SgNB). The processing circuitry may befurther configured to determine, based on inactivity of the UE, atransition of the UE from an RRC connected mode to an RRC inactive mode.The processing circuitry may be further configured to encode, fortransmission to the SgNB, an SgNB release request message that indicatesa partial suspension of the dual connectivity based on the transition ofthe UE from the RRC connected mode to the RRC inactive mode. As part ofthe partial suspension: a first portion of the configuration for the SCGis to be maintained and a second portion of the configuration for theSCG is to be released. The memory may be configured to store the SgNBrelease request message.

In Example 2, the subject matter of Example 1, wherein the first portionof the configuration may include a signaling radio bearer (SRB) betweenthe SgNB and the UE, and the second portion of the configuration mayinclude a data radio bearer (DRB) between the SgNB and the UE.

In Example 3, the subject matter of one or any combination of Examples1-2, wherein the first and second portions of the configuration mayinclude one or more parameters related to one or more of: a packet dataconvergence protocol (PDCP) layer and a service data applicationprotocol (SDAP) layer; or the first and second portions of theconfiguration may include one or more parameters related to one or moreof: a radio link control (RLC) layer and a medium access control (MAC)layer.

In Example 4, the subject matter of one or any combination of Examples1-3, wherein the processing circuitry may be further configured todetermine the inactivity of the UE based on an expiration of an RRCinactivity timer at the MgNB.

In Example 5, the subject matter of one or any combination of Examples1-4, wherein the processing circuitry may be further configured todecode, from the SgNB, control signaling that indicates the inactivityof the UE.

In Example 6, the subject matter of one or any combination of Examples1-5, wherein the processing circuitry may be further configured tomaintain a configuration for the MCG during the partial suspension ofthe dual connectivity.

In Example 7, the subject matter of one or any combination of Examples1-6, wherein the processing circuitry may be further configured todetermine that the UE is to be paged based on reception of a downlinkdata packet from the SgNB, the data packet to be forwarded to the UE.The downlink data packet may be received during the partial suspensionof the dual connectivity. The processing circuitry may be furtherconfigured to encode, for transmission to the UE, a paging message topage the UE for the downlink data packet.

In Example 8, the subject matter of one or any combination of Examples1-7, wherein the processing circuitry may be further configured todecode a measurement report received from the UE during a resumption ofthe dual connectivity. The measurement report may include a signalquality measurement, at the UE, for cells of the SgNB. The processingcircuitry may be further configured to determine, based at least partlyon the signal quality measurement, whether the dual connectivity is tobe resumed with the SgNB.

In Example 9, the subject matter of one or any combination of Examples1-8, wherein the processing circuitry may be further configured toexchange control signaling with the UE to establish an access stratum(AS) security. The processing circuitry may be further configured todetermine whether the dual connectivity is to be resumed with the SgNBbased on one or more measurement reports received from the UE, wherein:the measurement reports received from the UE after the AS security isestablished are used for the determination, and the measurement reportsreceived from the UE before the AS security is established are not usedfor the determination.

In Example 10, the subject matter of one or any combination of Examples1-9, wherein the processing circuitry may be further configured todecode a message received from the UE during the partial suspension ofthe dual connectivity. The message may include information related toconnectivity of the UE or location of the UE. The processing circuitrymay be further configured to determine, based on the information relatedto connectivity of the UE or location of the UE, whether the dualconnectivity is to be resumed with the SgNB.

In Example 11, the subject matter of one or any combination of Examples1-10, wherein the information related to connectivity of the UE orlocation of the UE may include one or more of: whether the UE is in acell in which a UE context is stored, whether the UE is in a samelocation as during a previous communication with the MgNB, and whetherthe SCG for the dual connectivity is valid.

In Example 12, the subject matter of one or any combination of Examples1-11, wherein the processing circuitry may be further configured toencode, for transmission to the UE, another message that indicateswhether the dual connectivity is to be resumed with the SgNB. The othermessage may be encoded in accordance with the AS security.

In Example 13, the subject matter of one or any combination of Examples1-12, wherein the apparatus may further include a transceiver totransmit the SgNB release request message.

In Example 14, the subject matter of one or any combination of Examples1-13, herein the processing circuitry may include a baseband processorto encode the SgNB release request message.

In Example 15, a computer-readable storage medium may store instructionsfor execution by one or more processors to perform operations forcommunication by a generation Node-B (gNB). The gNB may be configurableto operate as a master gNB (MgNB). The operations may configure the oneor more processors to encode radio-resource control (RRC) signaling toprovide configuration information for configuring a User Equipment (UE)with a secondary cell group (SCG) for dual connectivity to allow the UEto utilize radio resources of both a master cell group (MCG) associatedwith the MgNB and the SCG, the SCG associated with a secondary gNB(SgNB). The operations may further configure the one or more processorsto determine, based on inactivity of the UE, a transition of the UE froma radio resource control (RRC) connected mode to an RRC idle mode. Theoperations may further configure the one or more processors to encode,for transmission to the SgNB, an SgNB release request message thatindicates a release of the dual connectivity based on the inactivity ofthe UE. The operations may further configure the one or more processorsto determine that the UE is to be paged based on reception of a downlinkdata packet from the SgNB to be forwarded to the UE. The downlink datapacket may be received after the release of the dual connectivity. Theoperations may further configure the one or more processors to encode,for transmission to the UE, a paging message to page the UE to indicatetransmission, by the MgNB, of the downlink data packet.

In Example 16, the subject matter of Example 15, wherein the operationsmay further configure the one or more processors to encode the SgNBrelease request message for transmission to the SgNB on an Xx interfaceor an Xn interface.

In Example 17, an apparatus of a User Equipment (UE) may comprisememory. The apparatus may further comprise processing circuitry. Theprocessing circuitry may be configured to decode, from a masterGeneration Node-B (MgNB), first radio-resource control (RRC) signalingthat includes information for configuring the UE with a configurationfor a secondary cell group (SCG) for dual connectivity to allow the UEto utilize radio resources of both a master cell group (MCG) associatedwith the MgNB and the SCG, the SCG associated with a secondary gNB(SgNB). The processing circuitry may be further configured to decode,from the MgNB, second RRC signaling that indicates a partial suspensionof the dual connectivity. The processing circuitry may be furtherconfigured to, as part of the partial suspension of the dualconnectivity: maintain a first portion of the configuration for the SCG;and release a second portion of the configuration for the SCG. Thememory may be configured to store the signal quality measurement.

In Example 18, the subject matter of Example 17, wherein the processingcircuitry may be further configured to, during the suspension of thedual connectivity: monitor for paging messages from the MgNB; anddetermine a signal quality measurement based on a downlink signalreceived from the SgNB; and encode, for transmission to the MgNB, ameasurement report that indicates the signal quality measurement.

In Example 19, the subject matter of one or any combination of Examples17-18, wherein the signal quality measurement may be one of: a measuredradio frequency (RF) signal quality, a reference signal received power(RSRP), and a reference signal received quality (RSRQ).

In Example 20, the subject matter of one or any combination of Examples17-19, wherein the processing circuitry may be further configured toencode the measurement report to further indicate whether the signalquality measurement is for the SgNB or for another SgNB.

In Example 21, the subject matter of one or any combination of Examples17-20, wherein the first and second portions of the configuration mayinclude one or more parameters related to one or more of: a packet dataconvergence protocol (PDCP) layer and a service data applicationprotocol (SDAP) layer.

In Example 22, the subject matter of one or any combination of Examples17-21, wherein the first and second portions of the configuration mayinclude one or more parameters related to one or more of: a radio linkcontrol (RLC) layer and a medium access control (MAC) layer.

In Example 23, the subject matter of one or any combination of Examples17-22, wherein the first portion of the configuration may include asignaling radio bearer (SRB) between the SgNB and the UE. The secondportion of the configuration may include a data radio bearer (DRB)between the SgNB and the UE.

In Example 24, the subject matter of one or any combination of Examples17-23, wherein the processing circuitry may be further configured toencode, for transmission to the MgNB during the partial suspension ofthe dual connectivity, information related to connectivity of the UE orlocation of the UE.

In Example 25, the subject matter of one or any combination of Examples17-24, wherein the information related to connectivity of the UE orlocation of the UE may include one or more of: whether the UE is in acell in which a UE context is stored, whether the UE is in a samelocation as during a previous communication with the MgNB, and whetherthe SCG for the dual connectivity is valid.

In Example 26, the subject matter of one or any combination of Examples17-25, wherein the processing circuitry may be further configured todecode control signaling from the MgNB for an establishment of an accessstratum (AS) security. The processing circuitry may be furtherconfigured to encode the measurement report in accordance with the ASsecurity.

In Example 27, the subject matter of one or any combination of Examples17-26, wherein the UE may be configured with a first medium accesscontrol (MAC) entity for the MCG. The UE may be configured with a secondMAC entity for the SCG.

In Example 28, a generation Node-B (gNB) may be configurable to operateas a secondary gNB (SgNB). An apparatus of the gNB may comprise memory.The apparatus may further comprise processing circuitry. The processingcircuitry may be configured to decode, from a master Generation Node-B(MgNB), control signaling that includes configuration information forconfiguring a User Equipment (UE) with a secondary cell group (SCG) fordual connectivity to allow the UE to utilize radio resources of both amaster cell group (MCG) associated with the MgNB and the SCG, the SCGassociated with the SgNB. The processing circuitry may be furtherconfigured to decode, from the MgNB, an SgNB release request messagethat indicates a partial suspension of the dual connectivity, wherein: adata radio bearer (DRB) between the SgNB and the UE is to be released,and a signaling radio bearer (SRB) between the SgNB and the UE is to bemaintained. The processing circuitry may be further configured toforward, to the MgNB, a downlink data packet for the UE, the downlinkdata packet received from a serving gateway (SGW) during the partialsuspension of the dual connectivity. The memory may be configured tostore information related to the SgNB release request message.

In Example 29, the subject matter of Example 28, wherein the controlsignaling is first control signaling. The processing circuitry may befurther configured to determine, based on a time duration elapsed sincea previous uplink communication from the UE, whether the UE is to be putinto an inactive mode. The processing circuitry may be furtherconfigured to encode, for transmission to the MgNB over an Xx interfaceor an Xn interface, second control signaling that indicates whether theUE is to be put into an inactive mode.

In Example 30, a generation Node-B (gNB) may be configurable to operateas a master gNB (MgNB). An apparatus of the gNB may comprise means forencoding radio-resource control (RRC) signaling to provide configurationinformation for configuring a User Equipment (UE) with a secondary cellgroup (SCG) for dual connectivity to allow the UE to utilize radioresources of both a master cell group (MCG) associated with the MgNB andthe SCG, the SCG associated with a secondary gNB (SgNB). The apparatusmay further comprise means for determining, based on inactivity of theUE, a transition of the UE from a radio resource control (RRC) connectedmode to an RRC idle mode. The apparatus may further comprise means forencoding, for transmission to the SgNB, an SgNB release request messagethat indicates a release of the dual connectivity based on theinactivity of the UE. The apparatus may further comprise means fordetermining that the UE is to be paged based on reception of a downlinkdata packet from the SgNB to be forwarded to the UE. The downlink datapacket may be received after the release of the dual connectivity. Theapparatus may further comprise means for encoding, for transmission tothe UE, a paging message to page the UE to indicate transmission, by theMgNB, of the downlink data packet.

In Example 31, the subject matter of Example 30, wherein the apparatusmay further comprise means for encoding the SgNB release request messagefor transmission to the SgNB on an Xx interface or an Xn interface.

The Abstract is provided to comply with 37 C.F.R. Section 1.72(b)requiring an abstract that will allow the reader to ascertain the natureand gist of the technical disclosure. It is submitted with theunderstanding that it will not be used to limit or interpret the scopeor meaning of the claims. The following claims are hereby incorporatedinto the detailed description, with each claim standing on its own as aseparate embodiment.

What is claimed is:
 1. An apparatus, comprising: at least one processorconfigured to cause a master node to: encode radio-resource control(RRC) signaling to provide information for configuring a User Equipment(UE) with a configuration for a secondary cell group (SCG) for dualconnectivity to allow the UE to utilize radio resources of both a mastercell group (MCG) associated with the master node and the SCG, the SCGassociated with a secondary node; determine, based on inactivity of theUE, a transition of the UE from an RRC connected mode to an RRC inactivemode; and encode, for transmission to the secondary node, a secondarynode request message that indicates suspension of the dual connectivitybased on the determination of the transition of the UE from the RRCconnected mode to the RRC inactive mode; decode, from the secondarynode, a confirmation of the secondary node request message; decode, fromthe secondary node, a message based on data activity for the UE; andencode, for transmission to the secondary node, a resume message to thesecondary node.
 2. The apparatus of claim 1, wherein: a first portion ofthe configuration includes a signaling radio bearer (SRB) between thesecondary node and the UE, and a second portion of the configurationincludes a data radio bearer (DRB) between the secondary node and theUE.
 3. The apparatus of claim 1, wherein: first and second portions ofthe configuration include one or more parameters related to one or moreof: a packet data convergence protocol (PDCP) layer and a service dataapplication protocol (SDAP) layer, or the first and second portions ofthe configuration include one or more parameters related to one or moreof: a radio link control (RLC) layer and a medium access control (MAC)layer.
 4. The apparatus of claim 1, wherein the at least one processoris further configured to cause the master node to: determine theinactivity of the UE based on an expiration of an RRC inactivity timerat the master node.
 5. The apparatus of claim 1, wherein the at leastone processor is further configured to cause the master node to: decode,from the secondary node, control signaling that indicates the inactivityof the UE.
 6. The apparatus of claim 1, wherein when the secondary noderequest message indicates suspension of the dual connectivity: wherein,as part of the suspension, a first portion of the configuration for theSCG is to be maintained and a second portion of the configuration forthe SCG is to be released.
 7. The apparatus of claim 1, wherein the atleast one processor is further configured to cause the master node to:determine that the UE is to be paged based on reception of a downlinkdata packet from the secondary node, the data packet to be forwarded tothe UE, wherein the downlink data packet is received during thesuspension or release of the dual connectivity; and encode, fortransmission to the UE, a paging message to page the UE for the downlinkdata packet.
 8. The apparatus of claim 1, wherein the at least oneprocessor is further configured to cause the master node to: decode ameasurement report received from the UE during a resumption of the dualconnectivity, wherein the measurement report includes a signal qualitymeasurement, at the UE, for cells of the secondary node; determine,based at least partly on the signal quality measurement, whether thedual connectivity is to be resumed with the secondary node.
 9. Theapparatus of claim 1, wherein the at least one processor is furtherconfigured to cause the master node to: exchange control signaling withthe UE to establish an access stratum (AS) security; determine whetherthe dual connectivity is to be resumed with the secondary node based onone or more measurement reports received from the UE, wherein: themeasurement reports received from the UE after the AS security isestablished are used for the determination, and the measurement reportsreceived from the UE before the AS security is established are not usedfor the determination.
 10. The apparatus of claim 1, wherein the atleast one processor is further configured to cause the master node to:decode a message received from the UE during the suspension or releaseof the dual connectivity, wherein the message includes informationrelated to connectivity of the UE or location of the UE; and determine,based on the information related to connectivity of the UE or locationof the UE, whether the dual connectivity is to be resumed with thesecondary node.
 11. The apparatus of claim 10, wherein the informationrelated to connectivity of the UE or location of the UE includes one ormore of: whether the UE is in a cell in which a UE context is stored,whether the UE is in a same location as during a previous communicationwith the master node, and whether the SCG for the dual connectivity isvalid.
 12. The apparatus of claim 10, wherein the at least one processoris further configured to cause the master node to: encode, fortransmission to the UE, another message that indicates whether the dualconnectivity is to be resumed with the secondary node, wherein the othermessage is encoded in accordance with an access stratum (AS) security.13. A network node, comprising: at least one processor configured tocause the network node, operating as a master node, to: encoderadio-resource control (RRC) signaling to provide information forconfiguring a User Equipment (UE) with a dual connectivity (DC)configuration for a secondary cell group (SCG) for dual connectivity toallow the UE to utilize radio resources of both a master cell group(MCG) associated with the master node and the SCG, the SCG associatedwith a secondary node; determine, based on inactivity of the UE, atransition of the UE from an RRC connected mode to an RRC inactive mode;and encode, for transmission to the secondary node, a secondary noderequest message that indicates release of the DC configuration based onthe determination of the transition of the UE from the RRC connectedmode to the RRC inactive mode, wherein release of the DC configurationincludes keeping part of the DC configuration and releasing another partof the DC configuration; decode, from the secondary node, a confirmationof the secondary node request message; decode, from the secondary node,a message based on data activity for the UE; and encode, fortransmission to the secondary node, a resumption message to thesecondary node.
 14. The network node of claim 13, wherein the at leastone processor is further configured to cause the master node to:determine the inactivity of the UE based on an expiration of an RRCinactivity timer at the master node.
 15. The network node of claim 13,wherein the at least one processor is further configured to cause themaster node to: decode, from the secondary node, control signaling thatindicates the inactivity of the UE.
 16. The network node of claim 13,wherein when the secondary node request message indicates suspension ofthe dual connectivity: wherein, as part of the suspension, a firstportion of the configuration for the SCG is to be maintained and asecond portion of the configuration for the SCG is to be released.
 17. Anetwork node, comprising: at least one processor configured to cause thenetwork node, operating as a secondary node associated with a secondarycell group (SCG), to: decode, from a master node associated with amaster cell group (MCG), a secondary node request message that indicatessuspension of a dual connectivity (DC) of a user equipment (UE);determine, based on inactivity of the UE, a transition of the UE from aradio resource control (RRC) connected mode to an RRC inactive mode,wherein: the suspension of the DC is based on the determination, and theUE is configured via RRC signaling providing information for aconfiguration for the SCG, for DC to allow the UE to utilize radioresources of both the MCG and the SCG; encode, for transmission to themaster node, a confirmation of the secondary node request message;encode, for transmission to the master node, a message based on dataactivity for the UE; and decode, from the master node, a resume message.18. The network node of claim 17, wherein: the inactivity of the UE isfurther based on an expiration of an RRC inactivity timer at the masternode.
 19. The network node of claim 17, wherein the at least oneprocessor is further configured to cause the secondary node to: encode,for transmission to the master node, control signaling that indicatesthe inactivity of the UE.
 20. The network node of claim 17, wherein whenthe secondary node request message indicates suspension of the dualconnectivity: wherein, as part of the suspension, a first portion of theconfiguration for the SCG is to be maintained and a second portion ofthe configuration for the SCG is to be released.